Skip to content

Conversation

@aSeriousDeveloper
Copy link

  • start period allows for a grace period for the container to boot
  • start-interval allows for more frequent checking during this grace period
  • also slightly increased the standard interval once the container is healthy

Resolves #541

See my comment for reasoning behind the values I've chosen.

- start period allows for a grace period for the container to boot
- start-interval allows for more frequent checking during this grace period
- also slightly increased the standard interval once the container is healthy
@jaydrogers jaydrogers changed the base branch from main to release/v3.6 August 7, 2025 15:29
@jaydrogers jaydrogers deleted the branch serversideup:280-create-a-frankenphp-variation August 28, 2025 21:29
@jaydrogers jaydrogers closed this Aug 28, 2025
@jaydrogers
Copy link
Member

Sorry for the hiccup here, but could you try creating a new PR?

I had to move things in GitHub it automatically closed this PR. I don't see where I can update the branch into https://github.com/serversideup/docker-php/tree/280-create-a-frankenphp-variation

It won't let me change it when I press edit.

@jaydrogers jaydrogers reopened this Aug 28, 2025
@jaydrogers jaydrogers changed the base branch from release/v3.6 to 280-create-a-frankenphp-variation August 28, 2025 21:37
@jaydrogers
Copy link
Member

NVM, I got it. I accidentally deleted the source branch. That's why it closed. I will be reviewing this for 4.0 and will keep you posted 👍

Sorry for the confusion!

@jaydrogers jaydrogers moved this to 🤔 Evaluating in serversideup/php v4.0 Sep 23, 2025
@jaydrogers
Copy link
Member

I love this proposal! Thanks a ton for sharing this, I learned a lot.

I summarized the changes here. Your proposal is brilliant 💯

Option Description Old Value New Value
start-period start period provides initialization time for containers that need time to bootstrap. Probe failure during that period will not be counted towards the maximum number of retries. However, if a health check succeeds during the start period, the container is considered started and all consecutive failures will be counted towards the maximum number of retries. - 60s
start-interval start interval is the time between health checks during the start period. - 3s
timeout If a single run of the check takes longer than timeout seconds then the check is considered to have failed. 3s 3s
retries It takes retries consecutive failures of the health check for the container to be considered unhealthy. 3 3
interval The health check will first run interval seconds after the container is started, and then again interval seconds after each previous check completes. 5s 10s

@jaydrogers jaydrogers merged commit ad5fe47 into serversideup:280-create-a-frankenphp-variation Oct 2, 2025
12 of 86 checks passed
@github-project-automation github-project-automation bot moved this from 🤔 Evaluating to Done in serversideup/php v4.0 Oct 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Increase start_period for default healthcheck

2 participants